-- card: 4609 from stack: in.0-4 -- bmap block id: 13121 -- flags: 0000 -- background id: 8040 -- name: Ex 2.7 -- part 1 (button) -- low flags: 00 -- high flags: 0000 -- rect: left=233 top=183 right=244 bottom=308 -- title width / last selected line: 0 -- icon id / first selected line: 0 / 0 -- text alignment: 1 -- font id: 0 -- text size: 12 -- style flags: 0 -- line height: 16 -- part name: Different fonts in one field ----- HyperTalk script ----- -- The "HiliteRadio" handler is in the stack script. on mouseUp hide fld "feedback" HiliteRadio end mouseUp -- part 2 (button) -- low flags: 00 -- high flags: 0000 -- rect: left=75 top=184 right=249 bottom=138 -- title width / last selected line: 0 -- icon id / first selected line: 0 / 0 -- text alignment: 1 -- font id: 0 -- text size: 12 -- style flags: 0 -- line height: 16 -- part name: Different sized cards ----- HyperTalk script ----- -- The "HiliteRadio" handler is in the stack script. on mouseUp hide fld "feedback" HiliteRadio end mouseUp -- part 3 (button) -- low flags: 00 -- high flags: 0000 -- rect: left=162 top=180 right=248 bottom=216 -- title width / last selected line: 0 -- icon id / first selected line: 0 / 0 -- text alignment: 1 -- font id: 0 -- text size: 12 -- style flags: 0 -- line height: 16 -- part name: Multiple windows ----- HyperTalk script ----- -- The "HiliteRadio" handler is in the stack script. on mouseUp hide fld "feedback" HiliteRadio end mouseUp -- part 4 (button) -- low flags: 00 -- high flags: 0000 -- rect: left=324 top=179 right=250 bottom=416 -- title width / last selected line: 0 -- icon id / first selected line: 0 / 0 -- text alignment: 1 -- font id: 0 -- text size: 12 -- style flags: 0 -- line height: 16 -- part name: Different window styles ----- HyperTalk script ----- -- The "HiliteRadio" handler is in the stack script. on mouseUp hide fld "feedback" HiliteRadio end mouseUp -- part 13 (button) -- low flags: 00 -- high flags: A003 -- rect: left=402 top=296 right=316 bottom=461 -- title width / last selected line: 0 -- icon id / first selected line: 0 / 0 -- text alignment: 1 -- font id: 0 -- text size: 12 -- style flags: 0 -- line height: 16 -- part name: Done ----- HyperTalk script ----- -- The "checkOneRight" handler is in the stack script. on mouseUp checkOneRight end mouseUp -- part 14 (button) -- low flags: 00 -- high flags: A003 -- rect: left=352 top=320 right=338 bottom=463 -- title width / last selected line: 0 -- icon id / first selected line: 0 / 0 -- text alignment: 1 -- font id: 0 -- text size: 12 -- style flags: 0 -- line height: 16 -- part name: Correct Answer ----- HyperTalk script ----- -- This handler shows the correct answer. on mouseUp hideFeedback dehiliteBtns set hilite of btn 3 to true wait 25 repeat 2 set hilite of btn 3 to false wait 25 set hilite of btn 3 to true wait 25 end repeat ans 5 end mouseUp -- part contents for background part 9 ----- text ----- 7 of 8 -- part contents for background part 6 ----- text ----- You are thinking of making a catalogue stack that would have an index usable from any of the product cards in the stack. You want the index to be always visible, without obscuring any of the information on the product cards. Which feature of HyperCard would help you do this? -- part contents for background part 19 ----- text ----- No. Having different fonts in one field would not help you solve this problem. No, not quite. You might want to use a smaller card for the index, but there’s another feature that allows you to have both cards visible at the same time. Try again. Yes. Since HyperCard now supports multiple windows, you could put the index in a separate, smaller window that would sit to the side of the product card’s window. No. Appropriate use of background and card layers is important, but it won’t help you solve this problem. This is the correct answer. HyperCard now supports multiple windows, so you could put the index in a smaller window that would sit to the side of the product card’s window.